-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a parallel abstract class hierarchy for JDBC vs non-JDBC classes #24172
Conversation
Created a pure fork. Will spend time cleaning it up
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
/test connector=connectors/source-mysql
Build PassedTest summary info:
|
/test connector=connectors/source-bigquery
Build PassedTest summary info:
|
/test connector=connectors/source-mongodb-v2
Build FailedTest summary info:
|
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|---|---|---|
source-alloydb |
2.0.2 |
✅ | ✅ |
source-alloydb-strict-encrypt |
2.0.2 |
🔵 (ignored) |
🔵 (ignored) |
source-bigquery |
0.2.3 |
✅ | ✅ |
source-clickhouse |
0.1.16 |
✅ | ✅ |
source-clickhouse-strict-encrypt |
0.1.16 |
🔵 (ignored) |
🔵 (ignored) |
source-cockroachdb |
0.1.21 |
✅ | ✅ |
source-cockroachdb-strict-encrypt |
0.1.21 |
🔵 (ignored) |
🔵 (ignored) |
source-db2 |
0.1.18 |
✅ | ✅ |
source-db2-strict-encrypt |
0.1.18 |
🔵 (ignored) |
🔵 (ignored) |
source-dynamodb |
0.1.2 |
✅ | ✅ |
source-jdbc |
0.3.5 |
🔵 (ignored) |
🔵 (ignored) |
source-mongodb-strict-encrypt |
0.1.19 |
🔵 (ignored) |
🔵 (ignored) |
source-mongodb-v2 |
0.1.19 |
✅ | ✅ |
source-mssql |
1.0.3 |
✅ | ✅ |
source-mssql-strict-encrypt |
1.0.3 |
🔵 (ignored) |
🔵 (ignored) |
source-mysql |
2.0.3 |
✅ | ✅ |
source-mysql-strict-encrypt |
2.0.3 |
🔵 (ignored) |
🔵 (ignored) |
source-oracle |
0.3.23 |
✅ | ✅ |
source-oracle-strict-encrypt |
0.3.23 |
🔵 (ignored) |
🔵 (ignored) |
source-postgres |
2.0.3 |
✅ | ✅ |
source-postgres-strict-encrypt |
2.0.3 |
🔵 (ignored) |
🔵 (ignored) |
source-redshift |
0.3.16 |
✅ | ✅ |
source-scaffold-java-jdbc |
0.1.0 |
🔵 (ignored) |
🔵 (ignored) |
source-snowflake |
0.1.31 |
✅ | ✅ |
source-tidb |
0.2.3 |
✅ | ✅ |
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (0)
Connector | Version | Changelog | Publish |
---|
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Other Modules (0)
Actionable Items
(click to expand)
Category | Status | Actionable Item |
---|---|---|
Version | ❌ mismatch |
The version of the connector is different from its normal variant. Please bump the version of the connector. |
⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
|
Changelog | ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
❌ changelog missing |
There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog. | |
Publish | ⚠ not in seed |
The connector is not in the seed file (e.g. source_definitions.yaml ), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug. |
❌ diff seed version |
The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version. |
/test connector=connectors/source-postgres
Build FailedTest summary info:
|
This PR is part of #23808:
AbstractJdbcBaseSource
class to seperate the two hierarchies. This will inform what we can clean up and is common.AbstractNonJdbcSource
by removing cruft that is only relevant for JDBC classesFuture work:
AbstractJdbcBaseSource
and existingAbstractJdbcSource
. I suspect that we will be able to: (i) Remove a lot of redundant code. (ii) Create common util classes for shared code (e.g. constructing and decorating the read iterators)Why this intermediate stage? Since there is some duplicate code across the two forked abstract classes
I expect this to be a transient stage